Conversation
eladkal
approved these changes
Jul 4, 2025
Contributor
|
Thanks for the fix, Vincent! I saw green on the CI. Strange. |
Member
|
Sometimes. When you rebase or force push or reopen, Github Action go into a race condition that they do not actually start the "real" tests - only sometimes run a few of the internal tests (mergabilty etc.) Such PR will be green - but will have just 3 or 4 checks. This is exactly what happened I raised that issue 3 or 4 years ago to Github, that status "green" when non all expected tests had even a chance to run is a bad idea - but it's still unresolved. It happens very rarely though. |
Member
|
that's the right screenshot: 
You can see when you click "vie details" on the last action in merged PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Static checks are failing on main due to #52768. Fixing it
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.